Release 10.1A: OpenEdge Development:
Progress Dynamics Repository Reference

gsc_logical_service table — gscls

This table defines the logical services available to the application. A logical service is a separate process, running either locally or remotely, that requires connection parameters to establish communication between the client and the service. Logical service names are unique so that connection to the service can be completely abstracted from the developer.

The physical service determines the actual connection parameters. Which physical service is used is determined by combining the session type with the logical service.

Logical services for AppServer service types are AppServer partition names. Logical services for database connection service types are the logical database name.

This table supports the registration of services. The connect_at_startup field controls whether a service is connected at the start of a session. This would typically be set to YES unless the service type is a Web service. Web services can have slow connection performance, so setting them not to connect at session start is usually preferred.

Table 13–3 lists the table’s FLA, fields, and foreign keys.

Table 13–3: gsc_logical_service table information 

Table FLA	Fields (data type)	Foreign keys
gscls	logical_service_obj (Decimal) logical_service_code (Character) logical_service_description (Character) service_type_obj (Decimal) can_run_locally (Logical) system_owned (Logical) write_to_config (Logical) connect_at_startup (Logical)	logical_service_obj service_type_obj

Table 13–4 gives details of the table’s indexes.

Table 13–4: gsc_logical_service index information 

Index name	Elements	Type
XPKgsc_logical_service	logical_service_obj	Primary Unique
XAK1gsc_logical_service	logical_service_code	Unique
XIE1gsc_logical_service	logical_service_description	Nonunique
XIE2gsc_logical_service	service_type_obj	Nonunique